[DRAFT][18.0] Use session-level advisory lock for requeuing jobs#907
Draft
[DRAFT][18.0] Use session-level advisory lock for requeuing jobs#907
Conversation
Contributor
|
Hi @sbidoul, |
guewen
force-pushed
the
18.0-advisory-lock-requeue
branch
from
fed50d4 to
ffbc8f7
Compare
Member
|
I think we had considered that, but worried about potential conflicts with other advisory locks as it can potentially hit a wide range of lock ids. Not sure if we had thought about the two keys locks. As it is mentioned that the one key and two keys lock spaces do not overlap, maybe it's not an issue. cc/ @AnizR |
Member
|
Ah, pgbouncer. Folks using pgbouncer have it with transaction-level pooling which is not compatible with session level advisory locks? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.